2015-06-10 - 19859 - Spec - Japan EDI Upload Error - (Dan by 2015-07-24) #JapanSD #JapanABAP #OrderEntry #EDISD
SPECIFICATIONS
2015-05-13 - 19859 - Spec - Call offs creation failing for wrong season error (Japan)
Purpose
Create call offs using IDOCs (ROC) via GIS.
Admin Info
| Purpose |
Create call offs using IDOCs (ROC) via GIS |
| Requested By |
Daniel Brennan |
| Spec Created By |
Surya Basa |
| Spec Created Date |
06/15/2015 |
| Spec QA by |
Surya Basa |
| Objects |
ZSD_JPN_ORD_CALL_OFF |
| Document Status |
WIP |
Estimates
| Sl.No |
Activity |
Estimation in Hours |
| 1 |
Research |
|
| 2 |
Documentation |
|
| 3 |
Development/ Config |
|
| 4 |
Unit test in DEV |
|
| 5 |
Unit test in QUA |
|
| 6 |
Other activity |
|
| TOTAL |
References
Prior Tickets
[Provide links of prior associated Spec / Break Fix BOSS document(s)]2014-11-11 - 10735 - Spec - Program to create call offs with ref to Contracts for Japan cust. portal orders
Documents
[Attach any document(s) received for the requirement(s)] |
| SO-Japan.png |
Spec Changes
[List the changes made to program after the approval of the original requirement along with the Date on which the change request was received and the name of the initiator]
| Sl. |
Change Details |
Requested By |
Requested On |
Notes if any |
Functional Requirement
Purpose/WHY:
[Explain the purpose of the project and the reason why this requirement has come]It is proposed to use standard IDOCs (ROC format) to create call offs. There are currently four key customers that upload their orders to a customer portal and New Era downloads the details from the file which is a pre-defined format that is unique to each customer. A custom program needs to be developed to create a csv file (ROC format) from the upload file. Standard ORDERS IDOC will be used to process the csv file via GIS to create call-off(s).
In Scope:
[List the activities to be included in scope]- The custom program is restricted to Japan (SA-3200/10/00) and to order types ZOR.
- The program will generate the csv file with the required data (ROC) in addition to few new fields mentioned below.
- GIS will process the csv file via ORDERS IDOC and create call-off(s).
- The order created in SAP can contain call-off lines from multiple valid contracts as well as lines with no reference to a contract.
- If multiple contracts exist, then the earliest contract will be picked and order will go into delivery hold for customer service to resolve.
Out of Scope:
[Out of scope activities]The program is not global and other document types not mentioned above are not handled in the program.
Solution Summary
[Discuss this section with Requester and get approval prior to beginning work]
- PO Type: New PO type JCO (Japan call off) to be created to indicate call offs created via GIS->Upload program. The same should be mapped as default in GIS.
- Call offs will be created with PO type JCO.
Program
- Program will create a csv file similar to the ROC order file; standard IDOC type ORDERS will be used to create orders via GIS.
- The Idoc exit will check the PO type JCO on the IDOC to process the file.
- Validations will be done by the standard IDOCs and the programs will not carry out any validations.
- Standard IDOC errors created via EDI (ORDERS) will not be shown in the Ztable.
Test Plan
[List test scenarios/cases to be executed here]| Scenario |
Scenario Description |
ATP Check Z2=with Lead Time Z3= w/o Lead Time |
Contract |
Inventory |
Expected Results |
| 1 |
Multiple call-offs in input file, but each material has only 1 open valid contract; inventory is available |
Call offs should be created referencing the ref. contract |
|||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z3 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z3 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| 2 |
Multiple call-offs in input file, each material can have either 1 open valid contract or no Contract; Inventory may or may not be available |
Call offs should be created with reference where available; otherwise create standalone SO line. |
|||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z3 |
Single Contract |
Available |
Order line should be loaded with contract reference |
||
| Z3 |
Single Contract |
Not available |
Order line should be loaded with J0 rejection reason |
||
| Z3 |
No contract |
Not available |
Order line should be loaded w/o contract reference with J0 |
||
| Z2 |
No contract |
Not available |
Order line should be loaded w/o contract reference |
||
| Z2 |
No contract |
Available |
Order line should be loaded w/o contract reference |
||
| 3 |
Multiple call-offs in input file, each material has multiple open valid Contracts or no contract; Inventory available |
Call offs should be created referencing earliest RDD contract with ZJ delivery block and ZJ rejection |
|||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with first valid Contract & with delivery block and reject reason |
||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with first valid Contract & with delivery block and reject reason |
||
| Z3 |
Multiple Contract |
Available |
Order line should be loaded with first valid Contract & with delivery block and reject reason |
||
| 4 |
Some materials have valid open contracts but RDD is outside the contract validity dates; Inventory may or may not be available |
Materials with valid open contracts loaded with ref. Z2 materials w/o valid open contracts loaded w/o ref. Z3 materials w/o valid open contracts loaded w/J0 rej. Code |
|||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference. |
||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason |
||
| Z3 |
No contract |
Not available |
Order line should be loaded with J0 rejection reason because of no inventory and w/o contract reference. |
||
| Z3 |
No contract |
Available |
Order line should be loaded without contract reference. |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with contract reference. |
||
| Z2 |
Exists but not in Req Del Dt |
Available |
Order line should be loaded without any contract reference |
||
| 5 |
DUPLICATE ORDERS: If sales order already in system with (Sold-To+Ship-To+PO ); then load this order but put on delivery block on Order |
Call offs should be created with reference where available and w/o if not and with delivery block |
|||
| Z2 |
Single Contract |
Available |
Order line should be loaded with reference to contract and with delivery block |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with reference to contract and with delivery block |
||
| Z3 |
No contract |
Available |
Order line should be loaded w/o reference to contract and with delivery block |
||
| Z3 |
No contract |
Available |
Order line should be loaded w/o reference to contract and with delivery block |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with reference to contract and with delivery block |
||
| Z2 |
Single Contract |
Available |
Order line should be loaded with reference to contract and with delivery block |
||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with reference to 1st valid contract & with delivery block and reject reason |
||
| 6 |
Multiple call-offs exist in the input file for a contract line with SINGLE size. The first call-off consumes the entire contract quantity. Subsequent call-offs should be loaded in sales order w/o ref. |
Call offs should be created with reference for available and w/o reference where not available |
|||
| Z2 |
Single Contract |
Available |
Call off should be loaded with contract reference |
||
| Z2 |
No contract |
Available |
Sales order should be loaded w/o reference and inventory from free available should be consumed |
||
| 7 |
Multiple call-offs exist in the input file for a contract line with MULTIPLE sizes. The first call-off consumes ONE size fully but the contract line is still open due to other sizes. Subsequent call-offs for the consumed size should be loaded in sales order w/o ref. |
Call offs should be created with reference for open lines and w/o reference if no-open quantity on contract |
|||
| Z2 |
Single Contract |
Available |
1st call off should be created with contract reference and open contract quantity should be consumed for size 738 |
||
| Z2 |
Single Contract |
Available |
2nd call off should NOT be created with contract reference consuming inventory from free available w/o delivery block |
||
| 8 |
Requested Qty is greater than open contract quantity; inventory available |
Order is loaded w/reference and open contact Excess quantity should be loaded w/o reference |
|||
| Z2 |
Single Contract |
Available |
Entire order should be loaded with reference to the contract with the total quantity |
||
| Do not reference contracts with PO Type =JPC |
Load order w/o reference to PO |
||||
| Z2 |
Single Contract |
Available |
Order line should be loaded w/o reference to contract. |
||
| 9 |
Multiple contracts for same material - one PO Type = JPC and the other non-JPC. Call-offs will be created w/ref to non-JPC contract. |
Call-offs will be created w/ref to non-JPC contract. |
|||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with reference to Contract with PO type non-JPC. |
||
| 10 |
Several (at least 4) open contracts for the same material. Call-offs will be created w/ref to earliest non-JPC contract. |
||||
| Z2 |
Multiple Contract |
Available |
Order line should be loaded with reference to earliest Contract w/o PO type JPC and with ZJ block at header & rejection at item level. |
||
| 11 |
Requested Qty is greater than open contract quantity; inventory not available |
Order should load w/ref for open qty and w/o ref for excess. ATP should use Lead time |
|||
| Z2 |
Single |
Not Available |
Order line should be loaded with referece to contract |
||
| 12 |
Input Validation: BLANK PO - Do not load records with blank PO; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 13 |
Input Validation: BLANK SOLD TO - Do not load records with blank Sold-To; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 14 |
Input Validation: BLANK SHIP TO - Do not load records with blank Ship-To; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 15 |
Input Validation: Do not load if RDD blank or invalid; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 16 |
Input Validation: Do not load if Cancel date blank or invalid; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 17 |
Input Validation: Do not load if Quantity value ZERO or blank; log errors |
Call offs should not be loaded; log error |
|||
| Z2 |
Single Contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z2 |
Single Contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| Z3 |
No contract |
Available |
|||
| 18 |
Input Validation: Do not load if Invalid JAN ID/ Blank; log errors |
Call offs should not be loaded; log error |
|||
| Z3 |
No contract |
Available |
Entire order should not be loaded and error message should be logged into Zerror table - ZJPN_CALL_OFF |
||
| Z3 |
No contract |
Available |
|||
| 19 |
Repeat scenario 1 with materials not used above and w/o a valid season |
Call offs should be loaded with ZS rejection |
|||
| 20 |
Repeat scenario 1 with cancel and RDD in the past |
Call offs should be loaded with ZD rejection and cancel and RDD pushed out (180 days for RDD and 210 days for cancel date) |
FAQ's for Users
* To be updated post unit testing
Solution Details
[Provide complete technical details for configuration or programming here]
- ROC file format with out Contract Number
| Field Name |
Format |
Mapping |
Comments |
| Header Record |
There is no Fixed length, fields are separated by '~' and data type character |
||
| Record Indicator |
H |
||
| Internet Order Number |
Not Used |
This is generated in ROC System |
|
| Sales Organization |
Always 3200 |
||
| Distribution Channel |
Always 10 |
||
| Division |
Always 00 |
||
| Cust Id(Sold To) |
From File |
||
| Customer PO Number |
From File |
||
| Ship To |
From File |
||
| Sales Person |
Not Used |
||
| Order Date |
Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM) |
Current Date + Time 12 AM |
|
| Ship By Date |
Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM) |
From File + Time 12 AM |
|
| Cancel date |
Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM) |
From File + Time 12 AM |
|
| Payment Terms |
Not Used( Not Necessary, System will determine the Payment Term) |
||
| Carrier Service |
Not Used |
||
| Blank Field |
Blank |
||
| Customer Group |
Not Used ( Not Necessary, System will determine automatically) |
||
| Terms Override |
Not Used |
||
| Dealer Override |
Not Used |
||
| Contact Persons Phone |
Not Used |
||
| Contact Persons Fax |
Not Used |
||
| Contact Persons Email |
Not Used |
||
| Hard Coded Value |
Using Null |
GLPR or DOMA OR NULL |
|
| Hard Coded Value |
Always JCO |
Mapped in the IDOC to segment E1EDK14 with qualifier 019. |
|
| Item Record |
|||
| Record Indicator |
L |
||
| Internet Order Number |
Not Used |
This is generated in ROC System |
|
| Cust Id(Sold To) |
From File |
||
| Customer PO Number |
From File |
||
| Seq No |
Not Used |
Some sequence number generated in ROC System |
|
| UPC Id |
From File |
||
| Hard Coded Value |
Always 0.0 |
||
| Hard Coded Value |
Always 0 |
||
| Quantity |
From File |
||
| Sales Person |
Not Used |
||
| Ship To |
From File |
||
| Ship By Date |
Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM) |
From File + Time 12 AM |
Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 006. |
| Material |
10 Leading Zeroes + Material |
From MEAN Table based on UPC Number |
|
| Size |
From MEAN Table based on UPC Number |
||
| Cancel date |
Date(MM/DD/YYYY) + Time Hardcoded (12:00:00 AM) |
From File + Time 12 AM |
Currently this field is not mapped in IDOC, this should be mapped to segment E1J3P03 with qualifier 006. |
- ZJEDI Input File
| Field Name |
Format |
Comments |
| Header Record |
There is no Fixed length, fields are separated by ',' and data type character |
|
| Sold To |
||
| Ship To |
||
| Customer PO |
||
| Requested Deliver Date |
User Format ( For eg. US Users MM/DD/YYYY and Japan users yyyymmdd etc |
|
| Cancel Date |
User Format ( For eg. US Users MM/DD/YYYY and Japan users yyyymmdd etc |
|
| Jan Id or UPC Number |
||
| Quantity |
Issues
[List Issues / Bugs identified in configuration or development]
1. Quantity consumption is not checked in real time. Impact
- In-correct contract may be referenced
- Cannot split between contract and non-contract
- Contract could be over-consumed (standard behavior)
- Cannot assign to multiple contracts (starting from earliest) per customer request
A: Let SAP check the quantities
2. Create call-off(s) with contract reference in input file or should contract be referenced in user exit?
- If input file, should lines be split to reference multiple contract references?
A: No contract reference in the input file.
3. What should the PO type be for call-off(s) created using this process?
4. Does the global season logic need to apply for Japan call offs too
- post orders with rejection when there’s no valid season
- push out dates if cancel/RDD or both are in the past
- post orders with rejection if customer specific season is invalid
Assuming answer to the above Question is NO; the IDOCs with errors will fail.
A: Should work for ZJEDI call offs
5. Copy contract document date (AUDAT) to the call offs when created with reference?
A: Yes
6. Call-off(s) created using this process will not use PO # as reference and need modification to current user exit to exclude this logic for Japan
A: Confirmed